Graphical user interfaces (GUIs) for improvements in case management and docketing

ABSTRACT

Methods, systems and software include programmatically downloading over the Internet, at routine intervals of time as well as on demand, from an online computer system of the USPTO, data relating to patent properties that are associated with a customer number; and creating a docket based on the downloaded data, generating and displaying a report generated from the downloaded data, sending an alert (email or text message) that is based on the downloaded data, or any combination thereof. Data specific to a particular client also is provided to the client programmatically, with reports, alerts, docketing, or any combination thereof, further being provided for use by the client.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a U.S. continuation-in-part patentapplication of, and claims priority under 35 U.S.C. § 120 to, U.S.nonprovisional patent application Ser. No. 14/574,074, filed Dec. 17,2014, which patent application and any patents issuing therefrom arehereby incorporated by reference herein, and which '074 application is aU.S. nonprovisional patent application of, and claims priority under 35U.S.C. § 119(e) to, U.S. provisional patent application Ser. No.61/917,344, filed Dec. 17, 2013, which provisional patent application isincorporated by reference herein; and the present application is a U.S.nonprovisional patent application of, and claims priority under 35U.S.C. § 119(e) to, U.S. provisional patent application 62/396,756,filed Sep. 19, 2016, which provisional patent application isincorporated by reference herein. The present application furtherincorporates herein by reference U.S. patent application Ser. No.13/082,374 and any patent issuing therefrom; Ser. No. 12/891,785 and anypatent issuing therefrom; and 61/246,083.

The present application hereby incorporates herein by reference theentire disclosure of U.S. patent application Ser. No. 14/827,308, filedAug. 15, 2015, and any publications thereof or patents issuingtherefrom.

The present application relates to case management and docketingapparatus, systems, and methods utilizing the computer systems andservices provided by the U.S. Patent & Trademark Office under thePrivate PAIR branding, and hereby incorporates the disclosures—includingthe computer program listings and associated source code—of U.S. patentapplication Ser. Nos. 61/246,083; 12/891,782; 12/891,785; 13/082,374;13/836,764; and Ser. No. 13/837,126. A portion of this incorporateddisclosure is set forth below in the written description and in thedrawings for ease of reference.

The present application further extends such disclosures by the furtheradvancements and innovations disclosed herein that have been made sincethe filings of these earlier incorporated patent applications. In thisrespect, the present application extends the disclosures of theseapplications by inclusion of the following computer program listing,itself comprising source code representing improvements in theapparatus, systems, and methods disclosed in these earlier-filed patentapplications.

COPYRIGHT STATEMENT

All of the material in this patent document, including the computerprogram listing, is subject to copyright protection under the copyrightlaws of the United States and other countries. The copyright owner hasno objection to the facsimile reproduction by anyone of the patentdocument or the patent disclosure, as it appears in officialgovernmental records but, otherwise, all other copyright rightswhatsoever are reserved.

COMPUTER PROGRAM LISTING

Submitted concurrently herewith via the USPTO's electronic filingsystem, and incorporated herein by reference, are computer program filesincluding instructions, routines, and/or other contents of severalcomputer program. A table setting forth the name and size of each fileincluded in the computer program listing is included below.

File Name Creation Date Size (Bytes) Description ascify.txt Dec. 17,2013 37473 Assembly 20:27 Source Code nimvia.txt Dec. 17, 2013 21387117Visual Studio 20:20 2012 Solution ASCIFY.txt Sep. 19, 2017 37473Assembly 12:04 Source Code readme.txt Sep. 19, 2017 2923 Instructions12:04 cp11.txt Sep. 19, 2017 22478505 Visual Studio 11:56 2015 Solutioncp12.txt Sep. 19, 2017 22478162 Visual Studio 11:56 2015 Solutioncp13.txt Sep. 19, 2017 22477819 Visual Studio 11:57 2015 Solutioncp14.txt Sep. 19, 2017 22477476 Visual Studio 12:03 2015 Solutioncp15.txt Sep. 19, 2017 22477133 Visual Studio 12:03 2015 Solutioncp16.txt Sep. 19, 2017 22476790 Visual Studio 12:04 2015 Solutioncp17.txt Sep. 19, 2017 15753119 Visual Studio 12:04 2015 Solution

The file “readme.txt”, contains instructions for utilizing “ascify.txt”to extract information from the other files. The other files representsome or all of a compressed binary file that has been converted to asciiformat. These other files can be converted back to binary formatutilizing an assembly conversion program source code which is containedin “ascify.txt”. The readme file includes instructions for compiling andrunning this conversion program, as well as instructions for convertingthe other files to compressed, binary files.

The “nimvia” text file corresponds to a compressed, binary file thatrepresents a compressed zip file containing source code written inCSharp using Visual Studio 2012. The target environment forimplementations utilizing such source code is 32-bit or 64-bit WindowsXP, Vista, or 7.

This “cpl” text files correspond to a compressed, binary file whichincludes source code written in CSharp. In particular, this compressed,binary file includes six different file packages contained therein.Three of these are .zip files, while the other three are .tar.gz files.These files can be opened utilizing a decompression utility such as7Zip. These packages include code for various versions of softwareimplementing features in accordance with one or more preferredembodiments.

The .tar.gz packages represent software components designed to functiontogether. The .zip packages represent updated versions of the componentscontained in the .tar.gz packages, although these updated versions maynot be fully integrated with one another. It will be appreciated,however, that improvements disclosed in this code can be utilizedtogether.

BACKGROUND OF THE INVENTION

The present invention generally relates to patent case management anddocketing.

There exist many systems and methods for managing intellectual propertydata. For example, USPA Pub. No. 2005/0210009 to Tran discloses systemsand methods for providing an electronic file for intellectual propertyapplications by receiving electronic file wrapper information from apatent office; and generating a single electronic document for an entryin the electronic file wrapper information, the document having allimages for the entry consolidated therein.

The current state-of-the-art for patent case management and docketingfails to realize the full potential of Private PAIR and the XML datathat is made available by the U.S. Patent & Trademark Office (USPTO) topatent practitioners for download.

Current practices primarily rely on the physical docketing of USPTOcorrespondence that is received by practitioners via the U.S. PostOffice. Typically, one or more docket clerks open and review the USPTOcorrespondence, and then make manual data entries in a docket programfor creating and tracking deadlines that may be associated with theUSPTO correspondence. Sometimes this function is outsourced to a thirdparty service provider.

At single-practitioner firms and some smaller firms, the manual dataentry may be performed by the practitioner himself or herself. Moreover,the data may not even be entered into a docketing program, but insteadin a general purpose calendar program or spreadsheet that is notspecifically designed to address any particular patent case managementand patent docketing needs.

The manual data entry that is performed in these conventional practicesis generally duplicative of the data entry that has already beenperformed by the USPTO. In this regard, application data, includingUSPTO correspondence data, is already maintained in electronic form bythe USPTO and access to this data, via XML file downloads, is providedto patent practitioners by the USPTO in Private PAIR.

Accordingly, a need exists for improvement in patent case management anddocketing and, specifically, a need exists for making use of the XMLdata that is provided by the USPTO to patent practitioners in patentcase management and docketing. This, and other needs, are addressed byone or more embodiments of the invention.

SUMMARY OF THE INVENTION

The present invention includes many aspects and features. Moreover,while many aspects and features relate to, and are described in, thecontext of patent case management and docketing based on data downloadedfrom the USPTO, the present invention is not limited to use only inconnection with the USPTO, and it is contemplated that broad aspects ofthe invention encompass uses in connection with data that may beavailable for download from other patent offices, including the EuropeanPatent Office.

A first aspect relates to a computer-implemented method for presenting agraphical user interface (GUI) at a personal computer providing accessto information from an instance of an in-memory docket that is generatedon demand by a user without manual data entry of bibliographical ortransactional information of patent properties, the instance of thein-memory docket comprising information regarding patent properties thatare associated with a customer number at the U.S. Patent & TrademarkOffice. The method includes programmatically downloading, by thepersonal computer, from an online computer system of the United StatesPatent & Trademark Office, data relating to patent properties that areassociated with the customer number by programmatically accessing overthe Internet the online computer system using a Public keyInfrastructure digital certificate, and programmatically downloading tothe personal computer one or more XML files containing application datafor a customer number with which the Public key Infrastructure digitalcertificate is associated; programmatically constructing in transitorymemory of the personal computer, based on the downloaded data, thein-memory docket for the patent properties associated with the customernumber; and programmatically displaying the graphical user interfaceproviding access to information from the instance of an in-memorydocket, the graphical user interface comprising a matters display areaconfigured to display a row for each patent property representing amatter in the in-memory docket, the in-memory docket including a matterfor each patent property associated with the customer number, wherein auser can click on a row to select it, a matter details display areaconfigured to display details for a matter selected via the mattersdisplay area, and an events display area configured to display aplurality of rows each corresponding to an event for a matter selectedvia the matter display area.

In a feature of this aspect, the events configured to be displayed inthe events display area include events based on transaction informationfor a patent property.

In a feature of this aspect, the events configured to be displayed inthe events display area include events based on status information for apatent property.

In a feature of this aspect, the events configured to be displayed inthe events display area include events based on mail information for apatent property.

In a feature of this aspect, the events configured to be displayed inthe events display area include events based on image file wrapperinformation for a patent property.

In a feature of this aspect, the events display area comprises a searchbox configured search for events matching a search query.

In a feature of this aspect, the events display area comprises a filterrow configured to filter the events displayed in the events displayarea.

In a feature of this aspect, the graphical user interface furthercomprises a search box configured to allow a user to search for mattersmatching a search query.

In a feature of this aspect, the matters display area further comprisesa filter row configured to filter the matters displayed in the mattersdisplay area.

In a feature of this aspect, the matters display area is scrollable.

In a feature of this aspect, the events display area is scrollable.

In a feature of this aspect, the matters display area is displayed on aleft side of the graphical user interface.

In a feature of this aspect, the matters display area is displayed on aleft side of the graphical user interface, and the matter detailsdisplay area and the events display area are displayed on a right sideof the graphical user interface.

In a feature of this aspect, the matters display area is displayed on aleft side of the graphical user interface, the matter details displayarea and the events display area are displayed on a right side of thegraphical user interface, and the matter details display area isdisplayed above the events display area.

Another aspect relates to a computer-implemented method for presenting agraphical user interface (GUI) at a personal computer providing accessto information from an instance of an in-memory docket that is generatedon demand by a user without manual data entry of bibliographical ortransactional information of patent properties, the instance of thein-memory docket comprising information regarding patent properties thatare associated with a customer number at the U.S. Patent & TrademarkOffice. The method includes programmatically downloading, by thepersonal computer, from an online computer system of the United StatesPatent & Trademark Office, data relating to patent properties that areassociated with the customer number by programmatically accessing overthe Internet the online computer system using a Public keyInfrastructure digital certificate, and programmatically downloading tothe personal computer one or more XML files containing application datafor a customer number with which the Public key Infrastructure digitalcertificate is associated; programmatically constructing in transitorymemory of the personal computer, based on the downloaded data, thein-memory docket for the patent properties associated with the customernumber; and programmatically displaying, to a user via an electronicdisplay of the personal computer, the graphical user interface providingaccess to information from the instance of an in-memory docket, thegraphical user interface comprising a matters display area including arow for each patent property representing a matter in the in-memorydocket, the in-memory docket including a matter for each patent propertyassociated with the customer number, wherein a user can click on a rowto select it, a matter details display area including details for amatter selected via the matters display area, and an events display areaincluding a plurality of rows each corresponding to an event for amatter selected via the matter display area.

In accordance with an aspect of the invention, a system comprises a dataengine configured to download data from a USPTO web platform; an updatemodule configured to access data downloaded by the data engine, processit to produce information regarding patent properties, and post theproduced information to a repository; and a user interface moduleconfigured to access produced information from the repository andpresents a user interface to a user which presents various views of theinformation.

In accordance with an aspect of the invention, a method comprisesdownloading, by a data engine, data from a USPTO web platform;accessing, by an update module, data downloaded by the data engine,processing it to produce information regarding patent properties, andposting the produced information to a repository; and accessing, by auser interface module, the produced information from the repository andpresenting a user interface to a user which presents various views ofthe information.

In accordance with an aspect of the invention, a computer-readablemedium contains computer-executable instructions that, when executed bya computer, perform a method comprising the steps of: downloading, froman online computer system of the USPTO, data relating to patentproperties that are associated with a customer number; and creating adocket based on the downloaded data.

In a feature, the method is performed on a computer of a patentpractitioner or a law firm.

In a feature, the data that is downloaded is saved to local storage forlater access.

In a feature, the data that is downloaded is saved to cloud storage forlater access.

In a feature, the method further performs a step of determining whetherdata has been previously downloaded for the day and no download isperformed if data has already been downloaded. The method may performthe step of downloading the data from a cloud server if thedetermination is made that data has been previously been downloaded forthe day.

In a feature, the method further comprises accessing the online computersystem of the USPTO using a PKI digital certificate, and downloading anXML file containing application data for each customer number with whichthe PKI digital certificate is associated. Each of the steps of themethod are programmatically performed, and may performed on a routinebasis automatically without manual input from a user. Steps (a) and (b)further may be performed on demand by a user under the direction andcontrol of a patent practitioner. Furthermore, each of the steps (a) and(b) may be are performed after expiration of a predetermined period oftime; and each of the steps (a) and (b) may be programmaticallyperformed at a particular time of day or within a particular window oftime on one or more predetermined days.

In a feature, following step (a), the data that is downloaded isprocessed.

In a feature, following step (a), the data that is downloaded isconsolidated into an initial dataset, and the method further comprises:saving modifications to the initial dataset separately from the initialdataset, whereby the initial dataset itself is unchanged; andconstructing a working dataset by applying saved modifications to theinitial dataset. The saved modifications may be modifications made by adocket clerk, by a patent practitioner, or both in which case themodifications made by the docket clerk are applied before themodifications made by the patent practitioner are applied. The methodfurther may comprise the steps of creating a dataset comprising data fora particular client of the patent practitioner, and saving the clientdataset to a cloud location for later access by the client. Of course aswill be understood by the Ordinary Artisan, a dataset represents anin-memory cache of data retrieved from a data source and may beorganized in memory within rows of data tables or may be organizedwithin instances of a class object in an object-oriented programminglanguage, or combinations thereof.

In accordance with an aspect of the invention, a method comprises thesteps of: (a) downloading, from an online computer system of the USPTO,data relating to patent properties that are associated with a customernumber; and (b) creating a docket based on the downloaded data; (c)wherein said steps (a) and (b) are performed programmatically by aprogram that is executed on a computer.

In accordance with an aspect of the invention, a system comprises: (a) acomputer connected to the Internet; and (b) a program run by thecomputer; (c) wherein the computer, in accordance with the program beingrun, (i) programmatically downloads at routine intervals of time, froman online computer system of the USPTO, data relating to patentproperties that are associated with a customer number; and (ii) createsa docket based on the downloaded data.

In accordance with an aspect of the invention, a computer-readablemedium contains computer-executable instructions that, when executed bya computer, perform a method comprising the steps of: (a) downloading,from an online computer system of the USPTO, data relating to patentproperties that are associated with a customer number; and (b)generating and displays a report based on the downloaded data.

In a feature, following step (a), the data that is downloaded isconsolidated into an initial dataset from which the report is generated.The method further may include saving modifications to the initialdataset separately from the initial data set, and constructing a workingdataset by applying saved modifications to the initial dataset wherebythe initial dataset itself is unchanged, in which case the report thatis generated includes the modifications.

In another aspect, a method comprises the steps of: (a) downloading,from an online computer system of the USPTO, data relating to patentproperties that are associated with a customer number; and (b)generating and displays a report based on the downloaded data; (c)wherein said steps (a) and (b) are performed programmatically by aprogram that is executed on a computer.

In another aspect, a system comprises: (a) a computer connected to theInternet; and (b) a program run by the computer; (c) wherein thecomputer, in accordance with the program being run, (i) programmaticallydownloads at routine intervals of time, from an online computer systemof the USPTO, data relating to patent properties that are associatedwith a customer number; and (ii) generating and displays a report basedon the downloaded data.

In another aspect, a computer-readable medium containscomputer-executable instructions that, when executed by a computer,perform a method comprising the steps of: (a) downloading, from anonline computer system of the USPTO, data relating to patent propertiesthat are associated with a customer number; and (b) sending an emailalert based on the downloaded data.

In a feature, following step (a), the data that is downloaded isconsolidated into an initial dataset on which the email alert is based.The method further may include saving modifications to the initialdataset separately from the initial data set, and constructing a workingdataset by applying saved modifications to the initial dataset wherebythe initial dataset itself is unchanged, in which case the email alertis based on the initial dataset including the modifications appliedthereto.

In accordance with an aspect of the invention, a method comprises thesteps of: (a) downloading, from an online computer system of the USPTO,data relating to patent properties that are associated with a customernumber; and (b) sending an email alert based on the downloaded data; (c)wherein said steps (a) and (b) are performed programmatically by aprogram that is executed on a computer.

In accordance with an aspect of the invention, a system comprises: (a) acomputer connected to the Internet; and (b) a program run by thecomputer; (c) wherein the computer, in accordance with the program beingrun, (i) programmatically downloads at routine intervals of time, froman online computer system of the USPTO, data relating to patentproperties that are associated with a customer number; and (ii) sends anemail alert based on the downloaded data when a precondition is met.

In a feature, the precondition comprises any new updates to status ortransaction information for at least one of the patent properties forwhich data is downloaded.

In a feature, the email alert includes a report listing the updates.

In another aspect, a computer-readable medium containscomputer-executable instructions that, when executed by a computer,perform a method comprising the steps of: (a) downloading, from anonline computer system of the USPTO, data relating to patent propertiesthat are associated with a customer number; and (b) sending a textmessage to a mobile phone based on the downloaded data.

In another aspect, a computer-readable medium containscomputer-executable instructions that, when executed by a computer,perform a method comprising the steps of: (a) downloading, from a firstcloud, first patent data relating to patent properties of a person orlegal entity that are associated with a first customer number; (b)downloading, from a second cloud, second patent data relating to patentproperties of the same person or legal entity that are associated with asecond customer number; and (c) generating and displaying a consolidatedreport to the person or legal entity based on the first patent data andsecond patent data.

In a feature, the first cloud and the second cloud are the same.Alternatively, the first cloud and the second cloud are different.

In a feature of this aspect, the first customer number is associatedwith a first law firm and the second customer number is associated witha second, different law firm, and the first patent data and the secondpatent data both contain data on patent properties that are assigned toor under obligation of assignment to the person or entity.

In a feature, step (a) includes downloading the first patent data to acomputer of the person or entity, step (b) includes downloading thesecond patent data to the same computer of the person or entity, and theconsolidated report is generated and displayed on a display connected tothe computer of the person or entity.

Preferably, the computer-readable medium of the foregoing aspects thatcontains computer-executable instructions is non-transitory.

In another aspect, a non-transitory computer-readable medium containscomputer-executable instructions that, when executed by a personalcomputer of a patent practitioner, perform a method on the personalcomputer comprising the steps of: (a) programmatically downloading tothe personal computer of the patent practitioner, using a web browserrunning on the personal computer of the patent practitioner, from anonline computer system of the United States Patent & Trademark Office,data relating to patent properties that are associated with at least onecustomer number by (i) programmatically accessing over the Internet,with the web browser running on the personal computer of the patentpractitioner, the online computer system using a Public keyInfrastructure digital certificate, and (ii) programmaticallydownloading to the personal computer, through the access to the onlinecomputer system gained with the web browser running on the personalcomputer of the patent practitioner using the Public key Infrastructuredigital certificate, one or more XML files containing application datafor at least one customer number with which the Public keyInfrastructure digital certificate is associated; (b) programmaticallycreating, based on the downloaded data, in transitory memory of thepersonal computer, an in-memory docket for the patent propertiesassociated with the at least one customer number; and (c)programmatically displaying, through a graphical user interface at thepersonal computer, data of the in-memory docket for review by a userusing the personal computer, including displaying bibliographical andtransactional information of at least one of the patent properties forwhich data was downloaded. The steps result in an instance of anin-memory docket for the patent properties that are associated with theat least one customer number being programmatically created in thememory of the personal computer, based on the XML files downloaded tothe personal computer of the patent practitioner from the onlinecomputer system of the United States Patent & Trademark Office, withoutmanual data entry into the in-memory docket by the user ofbibliographical or transactional information of the patent properties.

In a feature, each of the steps of the method are programmaticallyperformed on a routine basis automatically without manual input from auser.

In a feature, each of the steps (a) and (b) are programmaticallyperformed after expiration of a predetermined period of time.

In a feature, each of the steps (a) and (b) are programmaticallyperformed at a particular time of day or within a particular window oftime on one or more predetermined days.

In a feature, the performed method further comprises calculatingdeadline reminders for the patent properties based on the downloadeddata for the patent properties and displaying the deadline remindersthrough the graphical user interface for review by a user.

In a feature, the performed method further includes enabling usermodifications to the data of the in-memory docket through the graphicaluser interface.

In a feature, the performed method further comprises identifying usermodifications that have been made to an instance of an in-memory docket,and applying the identified user modifications to another instance of anin-memory docket.

In a feature, the performed method further comprises identifying usermodifications that have been made to an instance of an in-memory docket,and uploading the identified user modifications to cloud storage forlater download to another personal computer having an instance of adocket to which the user modifications are applicable.

In a feature, the performed method further comprises downloading usermodifications that have been made to an instance of an in-memory docket,and applying the downloaded user modifications to another instance of anin-memory docket.

In a feature, the downloaded user modifications are user modificationsperformed by a docket clerk, and wherein the personal computer on whichthe user modifications are applied is a personal computer of a patentpractitioner.

In a feature, the performed method further comprises writing,programmatically from transitory memory of the personal computer, thedata of the in-memory docket to a non-transitory computer-readablemedium such that the data of the in-memory docket can be read back intotransitory memory of the personal computer after a reboot of thepersonal computer.

In another aspect, a non-transitory computer-readable medium containscomputer-executable instructions that, when executed by a personalcomputer of a patent practitioner, perform a method comprising the stepsof: (a) programmatically downloading to the personal computer of thepatent practitioner, using a web browser running on the personalcomputer of the patent practitioner, from an online computer system ofthe United States Patent & Trademark Office, data relating to patentproperties that are associated with a customer number by (i)programmatically accessing, with the web browser running on the personalcomputer of the patent practitioner, the online computer system using aPublic key Infrastructure digital certificate, and (ii) programmaticallydownloading to the personal computer of the patent practitioner, throughthe access to the online computer system gained with the web browserrunning on the personal computer of the patent practitioner using thePublic key Infrastructure digital certificate, one or more XML filescontaining application data for a customer number with which the Publickey Infrastructure digital certificate is associated; and (b) if a firstin-memory docket exists at the personal computer, then programmaticallyupdating the first in-memory docket at the personal computer based onthe downloaded data for the patent properties associated with thecustomer number, else creating a first in-memory docket at the personalcomputer based on the downloaded data for the patent propertiesassociated with the customer number; and thereafter (c) if a secondin-memory docket exists at the personal computer, then programmaticallyidentifying any user modifications in the second in-memory docket; and(d) programmatically creating a new second in-memory docket as afunction of any identified user modifications and the first in-memorydocket such that the second in-memory docket comprises the downloadeddata as overwritten by any user modifications; (e) wherein the secondin-memory docket represents a docket that is programmatically createdfrom data downloaded from the online computer system of the UnitedStates Patent & Trademark Office as changed thereafter by any usermodifications.

In another aspect, a method for presenting, on demand by a user withoutmanual data entry of bibliographical or transactional information ofpatent properties, an instance of an in-memory docket on a personalcomputer of the user for patent properties that are associated with acustomer number at the U.S. Patent & Trademark Office, comprises thesteps of: (a) programmatically downloading to the personal computer ofthe user, using a web browser running on the personal computer of theuser, from an online computer system of the United States Patent &Trademark Office, data relating to patent properties that are associatedwith a customer number by (i) programmatically accessing over theInternet, with the web browser running on the personal computer of theuser, the online computer system using a Public key Infrastructuredigital certificate, and (ii) programmatically downloading to thepersonal computer, through the access to the online computer systemgained with the web browser running on the personal computer of the userusing the Public key Infrastructure digital certificate, one or more XMLfiles containing application data for a customer number with which thePublic key Infrastructure digital certificate is associated; (b)programmatically constructing in transitory memory of the personalcomputer, based on the downloaded data, an in-memory docket for thepatent properties associated with the customer number; and (c)programmatically displaying, through a graphical user interface at thepersonal computer, data of the in-memory docket for review by a userusing the personal computer, including displaying bibliographical andtransactional information of the patent properties.

In another aspect, a system in which multiple instances are separatelycreated by different users of an in-memory docket for the same patentproperties associated with a particular customer number at the U.S.Patent & Trademark Office, comprising a plurality of computers connectedto the Internet, each personal computer corresponding to one of theusers and comprising non-transitory computer readable medium containingcomputer-executable instructions that, when executed on the personalcomputer of the respective user, perform a method comprising the stepsof: (a) programmatically downloading to the personal computer of therespective user, using a web browser running on the personal computer ofthe respective user, from an online computer system of the United StatesPatent & Trademark Office, data relating to patent properties that areassociated with the particular customer number by accessing over theInternet, with the web browser running on the personal computer of therespective user, the online computer system using a Public keyInfrastructure digital certificate, and downloading to the personalcomputer of the respective user, through the access to the onlinecomputer system gained with the web browser running on the personalcomputer of the respective user using the Public key Infrastructuredigital certificate, one or more XML files containing application datafor the particular customer number with which the Public keyInfrastructure digital certificate is associated; (b) programmaticallycreating, based on the downloaded data, in transitory memory of thepersonal computer, an in-memory docket for the patent propertiesassociated with the particular customer number; and (c) programmaticallydisplaying, through a graphical user interface at the personal computer,data of the in-memory docket for review by a user using the personalcomputer, including displaying bibliographical and transactionalinformation of the patent properties; wherein an independent instance ofan in-memory docket for the patent properties that are associated withthe particular customer number is programmatically created in the memoryof each respective personal computer of each respective user, based onthe XML files separately downloaded to the respective personal computersof the respective users from the online computer system of the UnitedStates Patent & Trademark Office, without manual data entry into thein-memory docket of bibliographical or transactional information of thepatent properties.

In a feature, the performed method with respect to one or more of thepersonal computers further comprises calculating deadline reminders forthe patent properties based on the downloaded data for the patentproperties and displaying the deadline reminders through the graphicaluser interface for review by a user.

In a feature, the performed method with respect to one or more of thepersonal computers further includes enabling user modifications to thedata of the in-memory docket through the graphical user interface. Theperformed method with respect to one or more of the personal computersmay further comprise identifying user modifications that have been madeto an instance of an in-memory docket, and applying the identified usermodifications to another instance of an in-memory docket; identifyinguser modifications that have been made to an instance of an in-memorydocket, and uploading the identified user modifications to cloud storagefor later download to another of the personal computers; and downloadinguser modifications that have been made to an instance of an in-memorydocket on another one of the personal computers, and applying thedownloaded user modifications to another instance of an in-memorydocket.

Additionally, optimizations and processes are included in the foregoingdisclosed embodiments, aspects and features that are believed tominimize accessing the online computer system of the USPTO and/orfacilitate efficient and synergistic case management and docketing.

In such respects, features of this aspect include, storing dataassociated with a digital certificate of a practitioner at a server andfirst downloading data from the server when using the digitalcertificate, checking the data for timeliness, and then proceeding todownload data from the USPTO when the data downloaded from the server isdetermined to outdated; storing data associated with a particularcustomer number at a server and first downloading data from the serverwhen using a digital certificate associated with the particular customernumber, checking the data for timeliness, and then proceeding todownload data from the USPTO when the data associated with theparticular customer number that is downloaded from the server isdetermined to be outdated. In either feature, once data is downloadedfrom the USPTO either for a customer number or a digital certificate,the data is uploaded to the server in association therewith for thebenefit of others associated with the customer number of using thedigital certificate. In addition to data associated with a particularcustomer number or a particular digital certificate, for data that ispublicly available, such data that is downloaded by a practitioner alsomay be uploaded to a server for use by others seeking the same data.These additional optimizations and processes preferably areprogrammatically performed without action by a user.

Additional aspects comprise improvements in the user interface,including functionality and associated layout of the user controls. Forexample, a docketing and case management system is provided having an“Excel” or spreadsheet feel to it for users, wherein all of the data isavailable in grid form with direct access to the underlying data withoutsearching for and modifying individual records, as experienced currentdocketing systems. As another example, a tab control is provided inwhich a first tab represent a listing of cases; another tab represents alisting of events found in all of the cases, including all status,transaction, mail, and image file wrapper events, whereby cases can be‘looked up’ and directly viewed based on an events listing; and anothertab includes deadline reminders that are programmatically generatedbased on events.

A user interface also preferably is provided for adding, deleting, andmodifying rule sets for generating reminders, with reminders beinggenerated on user demand as well as programmatically with existingreminders being updated with revised deadlines, where appropriate andwhere such deadlines have not been marked reviewed or completed by theuser. The arrangement of information and user controls is believed to beinnovative over currently existing systems and is believed to provide asynergy and efficiently in case management and docketing that is notrealized by conventional systems. Additional tabs may be provided formanaging invention disclosures, email alerts, and subsets of the datathat are published to clients through ‘clouds’ made accessible toclients respectively.

In additional features, the case listing includes a plurality of views,including a docket inventory listing, a reverse chronologicaltransactions listing, a status listing, an examiner listing, a datadownload audit listing, a priority fields listing, an ownership listing,and a publications listing. The status, transactions, and examinerslisting preferably is grouped by status, transaction date, and examinername respectively. Moreover, as there may be a significant number ofdifferent events, each preferably is mapped to a predefined short listof transactions and status descriptions, or ignored outright if nomapping is provided, whereby an efficient and ‘noiseless’ listing ofstatus and transactions may be provided.

Other aspects and features relate to innovative functionality disclosedin software including as a computer program listing.

In addition to the aforementioned aspects and features of the presentinvention, it should be noted that the present invention furtherencompasses the various possible combinations and subcombinations ofsuch aspects and features. Thus, for example, any aspect may be combinedwith an aforementioned feature in accordance with the present inventionwithout requiring any other aspect or feature.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more preferred embodiments of the present invention now will bedescribed in detail with reference to the accompanying drawings, whereinthe same elements are referred to with the same reference numerals.

FIG. 1 is a schematic illustration of a system architecture in whichinformation about patent properties is acquired electronically from theUSPTO by a patent practitioner using a computer, which may include adesktop pc, laptop, or server of the practitioner, and thenelectronically saved to local data storage of the practitioner.

FIGS. 1A and 1B are flowcharts illustrating steps of one or morepreferred embodiments in accordance with this first system architectureof FIG. 1.

FIG. 2 is a schematic illustration of another system architecture.

FIG. 2A is a flowchart illustrating steps of one or more preferredembodiments in accordance with the system architecture of FIG. 2.

FIG. 3 is a schematic illustration of another system architecture.

FIGS. 3A and 3B are flowcharts illustrating steps of one or morepreferred embodiments in accordance with the system architecture of FIG.3.

FIG. 4 is a schematic illustration of another system architecture.

FIG. 5 is a schematic illustration of another system architecture.

FIG. 6 is a schematic illustration of another system architecture.

FIG. 7 is a screenshot of a graphical user interface with user controlsshowing a first page of a tab control in accordance with one or morepreferred embodiments of the invention.

FIG. 8 is a screenshot of a graphical user interface with user controlsshowing a first page of a tab control in accordance with one or morepreferred embodiments of the invention.

FIG. 9 is a screenshot of a graphical user interface with user controlsshowing a first page of a tab control in accordance with one or morepreferred embodiments of the invention.

FIG. 10 is a screenshot of a graphical user interface with user controlsshowing a first page of a tab control in accordance with one or morepreferred embodiments of the invention.

FIG. 11 is a screenshot of a graphical user interface with user controlsshowing a first page of a tab control in accordance with one or morepreferred embodiments of the invention.

FIG. 12 is a screenshot of a graphical user interface with user controlsshowing a first page of a tab control in accordance with one or morepreferred embodiments of the invention.

FIG. 13 is a screenshot of a graphical user interface with user controlsshowing a first page of a tab control in accordance with one or morepreferred embodiments of the invention.

DETAILED DESCRIPTION

As a preliminary matter, it will readily be understood by one havingordinary skill in the relevant art (“Ordinary Artisan”) that theinvention has broad utility and application. Furthermore, any embodimentdiscussed and identified as being “preferred” is considered to be partof a best mode contemplated for carrying out the invention. Otherembodiments also may be discussed for additional illustrative purposesin providing a full and enabling disclosure of the invention.Furthermore, an embodiment of the invention may incorporate only one ora plurality of the aspects of the invention disclosed herein; only oneor a plurality of the features disclosed herein; or combination thereof.As such, many embodiments are implicitly disclosed herein and fallwithin the scope of what is regarded as the invention.

Accordingly, while the invention is described herein in detail inrelation to one or more embodiments, it is to be understood that thisdisclosure is illustrative and exemplary of the invention, and is mademerely for the purposes of providing a full and enabling disclosure ofthe invention. The detailed disclosure herein of one or more embodimentsis not intended, nor is to be construed, to limit the scope of patentprotection afforded the invention in any claim of a patent issuing herefrom, which scope is to be defined by the claims and the equivalentsthereof. It is not intended that the scope of patent protection affordedthe invention be defined by reading into any claim a limitation foundherein that does not explicitly appear in the claim itself.

Thus, for example, any sequence(s) and/or temporal order of steps ofvarious processes or methods that are described herein are illustrativeand not restrictive. Accordingly, it should be understood that, althoughsteps of various processes or methods may be shown and described asbeing in a sequence or temporal order, the steps of any such processesor methods are not limited to being carried out in any particularsequence or order, absent an indication otherwise. Indeed, the steps insuch processes or methods generally may be carried out in variousdifferent sequences and orders while still falling within the scope ofthe invention. Accordingly, it is intended that the scope of patentprotection afforded the invention is to be defined by the issuedclaim(s) rather than the description set forth herein.

Additionally, it is important to note that each term used herein refersto that which the Ordinary Artisan would understand such term to meanbased on the contextual use of such term herein. To the extent that themeaning of a term used herein—as understood by the Ordinary Artisanbased on the contextual use of such term—differs in any way from anyparticular dictionary definition of such term, it is intended that themeaning of the term as understood by the Ordinary Artisan shouldprevail.

Regarding applicability of 35 U.S.C. 112(f), no claim element isintended to be read in accordance with this statutory provision unlessthe explicit phrase “means for” or “step for” is actually used in suchclaim element, whereupon this statutory provision is intended to applyin the interpretation of such claim element.

Furthermore, it is important to note that, as used herein, “a” and “an”each generally denotes “at least one,” but does not exclude a pluralityunless the contextual use dictates otherwise. Thus, reference to “apicnic basket having an apple” describes “a picnic basket having atleast one apple” as well as “a picnic basket having apples.” Incontrast, reference to “a picnic basket having a single apple” describes“a picnic basket having only one apple.”

When used herein to join a list of items, “or” denotes “at least one ofthe items,” but does not exclude a plurality of items of the list. Thus,reference to “a picnic basket having cheese or crackers” describes “apicnic basket having cheese without crackers”, “a picnic basket havingcrackers without cheese”, and “a picnic basket having both cheese andcrackers.” When used herein to join a list of items, “and” denotes “allof the items of the list.” Thus, reference to “a picnic basket havingcheese and crackers” describes “a picnic basket having cheese, whereinthe picnic basket further has crackers,” as well as describes “a picnicbasket having crackers, wherein the picnic basket further has cheese.”

Referring now to the drawings, one or more preferred embodiments of theinvention are next described. The following description of one or morepreferred embodiments is merely exemplary in nature and is in no wayintended to limit the invention, its implementations, or uses.

Customer Numbers and PKI Digital Certificate

The U.S. Patent & Trademark Office (USPTO) maintains information aboutpatent properties—including both patent applications and patents—inelectronic form. Furthermore, the USPTO is now maintaining the officialfile records of current patent applications in electronic form.

In connection with this, the USPTO now makes data regarding patentproperties electronically accessible to the public via Public PAIR, andelectronically accessible to patent practitioners via Private PAIR. BothPublic PAIR and Private PAIR are available and widely accessible overthe Internet. Moreover, the data that is now accessible to a particularpatent practitioner via Private PAIR includes not only information thatis available via Public PAIR, but also information about patentproperties for which that patent practitioner is responsible and whichis not yet publicly available. The USPTO accomplishes this usingcustomer numbers and PKI digital certificates.

In particular, a customer number is a five or six digital number thatuniquely identifies: a person or legal entity; correspondence addressfor such entity; and a list of one or more patent practitioners, eachpractitioner being identified by his or her respective U.S. registrationnumber. The USPTO electronically maintains the customer numberinformation for each customer number.

The USPTO generally will issue a customer number in response to arequest from a patent practitioner. A law firm is not limited to havinga single customer number and may have more than one customer number. Forinstance, a law firm may request an additional customer number to beused in connection with all patent properties for a particular client ofthe law firm.

The customer number facilitates the identification of a correspondenceaddress for patent properties as well as identification of those patentpractitioners who can legally represent a patent applicant before theUSPTO. Specifically, a customer number usually is identified inconnection with the correspondence address for a patent property, andthe customer number usually is identified in connection with a power ofattorney in a patent property. Upon such identification in connectionwith the correspondence address, the USPTO thereafter associates theparticular patent property with the identified customer number.

A PKI digital certificate is issued by the USPTO to a patentpractitioner upon request. The USPTO maintains an association betweeneach PKI digital certificate and the patent practitioner to which thePKI digital certificate is issued. The PKI digital certificate is usedto authenticate a patent practitioner to the USPTO when accessingPrivate PAIR over the Internet.

Based on the associations maintained by the USPTO of: customer numberswith patent properties; patent practitioners with customer numbers; andPKI digital certificates with patent practitioners, a patentpractitioner who has been issued a PKI digital certificate generally isable to access information via Private PAIR for all patent propertiesassociated with customer numbers that include that patent practitioner'sregistration number. Such access includes the ability to viewinformation online about those patent properties as well as the abilityto download XML files that include data about those patent properties.Moreover, the data is available for download on a customer number bycustomer number basis. Thus, for example, an XML file download isavailable for each customer number with which the patent practitioner isassociated.

A First System Architecture

One or more preferred embodiments of the present invention are nowdescribed in connection with FIGS. 1-1 b.

FIG. 1 is a schematic illustration of a system architecture in whichinformation about patent properties is acquired electronically from theUSPTO 10 by a patent practitioner 12 using a computer, which may includea desktop pc, laptop, or server of the practitioner, and thenelectronically saved to local data storage 14 of the practitioner. FIG.1a is a flowchart illustrating steps of one or more preferredembodiments in accordance with this first system architecture.

Specifically, the patent practitioner accesses, via the Internet,Private PAIR and downloads 16 from the USPTO, for each customer numberwith which the patent practitioner is associated, the XML data for allof the patent properties associated with that customer number. Such dataconventionally may be manually downloaded by navigating to the customernumber filter in Private PAIR, selecting a desired customer number, andthen selecting the orange “XML” button. However, in accordance withpreferred embodiments, the downloading is programmatically performed ondemand, automatically at a scheduled time, or automatically after apredetermined period of time has elapsed.

Optionally, detailed XML data may be separately downloaded for each ofone or more specific patent properties for purposes of supplementing theinformation about such patent property that is contained in the customernumber download. Such a download includes detailed information that isnot included in the general customer number download, such as a historyof transactions and outgoing correspondence for the specific patentproperty, and title and continuity information of the specific patentproperty. This information can be important, for example, in bettercalculating deadlines when docketing. The detailed XML dataconventionally may be manually downloaded by navigating to theApplication Data tab for the particular patent property in Private PAIRand then selecting the orange “XML” button. However, in accordance withone or more preferred embodiments, the downloading is programmaticallyperformed when certain conditions are met that indicate such detailedinformation is needed.

Once the download customer number XML data is complete, the XML datafrom the downloaded files is processed 18 resulting in an initialdataset comprising a plurality of data tables. During the processing,the data from each of the downloaded XML files is reformatted andconsolidated together. The data tables include an Application Data Tablein which primary information about patent properties is stored; a Statusand Transaction Data Table in which status and transaction data isstored; and a Correspondence Data Table in which outgoing correspondenceinformation sent by the USPTO in connection with the patent propertiesis stored. The initial dataset is in the form of an in-memory datasetand is saved as one or more XML files. The initial dataset is saved 20to local storage, such as on a hard disk drive, flash drive, or otherlocal storage.

It will be appreciated that, rather than use in-memory datasets, one ormore databases may be used. For example, objects may be used instead ofdata tables, and the objects may be stored, accessed, and manipulatedusing a database management system such as DB4O.

Also during processing, additional data may be derived from the datathat has been downloaded from the USPTO and saved, including deadlinesthat may be calculated from the downloaded data. The derived data may beincluded in one or more data tables of the initial dataset. Forinstance, reminders regarding deadlines can be derived from thedownloaded data and then saved in a reminders data table of the initialdataset.

Provided there are no previous modifications or additions by thepractitioner that need to be accounted for (thus permitting steps 22 and24 to be skipped in FIG. 1a ), the initial dataset is used to generateand display reports to the patent practitioner; to generate and sendalerts and reports via email to the patent practitioner, or otherdesired recipients; and to instantiate a docket of the patentpractitioner. Additionally, the data may be filtered when generatingreports, alerts or instantiating a docket so that only those patentproperties of particular interest are included. Alternatively, suchfiltering may be performed when the initial dataset is created.

On the other hand, there may be modifications or additions to the dataof the initial dataset. In this respect, the practitioner may desire tomodify the data in the initial dataset after downloading—includingupdating, revising, and omitting data—or may desire to add data for usein reports, alerts, and docketing, such as data for new matters that arenot reflected in the data downloaded from the USPTO. The patentpractitioner is able to modify and add 26 data via different graphicaluser interfaces, including the ability to add matters and to addreminders for specific matters. The modifications and additions are madeto the in-memory dataset representing the initial dataset. The resultingin-memory dataset constitutes a working practitioner dataset (PracDs),and the reports, alerts, and docket are all generated based on thePracDs rather than the initial dataset.

A practitioner modifications (PM) dataset is created 28 in which the netmodifications and additions to the initial dataset are maintained. Thenet modifications and additions comprise the differences in the PracDsover the initial dataset. The PM is saved 30 to the local storageseparate and apart from the initial dataset. The initial dataset isthereby maintained in a pristine form based on the XML data that isacquired from the USPTO, and is not altered by any modifications oradditions that are be made by the practitioner.

Furthermore, when net modifications and additions have previously beensaved to local storage, the net modifications and changes are read fromthe local storage 20 and applied 22 to the resulting initial datasetthat is created following the download in order to create the PracDs foruse in reports, alerts and docketing. Thus, steps 22 and 24 are notskipped. Instead, the PracDs is constructed each time XML data isdownloaded from the USPTO by applying the PM to the initial dataset.

It is believed that the data that is available for download via PrivatePAIR is updated daily, and that only one download per day is necessary.Consequently, it will be appreciated that if the XML data has beendownloaded for the day, and if the PracDs needs to be constructed forreports, alerts and docketing, then the PracDs can be constructed byreading 32 the previously saved initial dataset from local storagewithout accessing Private PAIR and downloading the XML data from theUSPTO. Accordingly, a check may be performed before initiating XML datadownloading form the USPTO, and the download may occur if the XML datahas not yet been downloaded for the day and the XML data is needed.However, if the check indicates that the XML data has already beendownloaded for the particular day, then no download from the USPTO isinitiated, and the initial dataset created from the XML data that hasalready been downloaded for that particular day is read from localstorage for constructing the PracDs.

The check may include maintaining a timestamp for each XML downloadassociated with a customer number and deeming any download occurringafter a preset time as having obtained, for that day and for thatcustomer number, the most recent XML data available for that customernumber.

The ability to construct the PracDs from the initial dataset after theXML data has been downloaded from the USPTO on a particular day can beparticularly beneficial, as the downloading of the XML data from theUSPTO may take an appreciable amount of time that may be noticeable to auser seeking to work with and waiting for the PracDs to be constructed.Additionally, if Private PAIR is down or otherwise unavailable, thePracDs still can be constructed for reports, alerts and docketing byusing the most recently saved initial database and PM. This ability toread and construct the PracDs from local storage under such scenarios isreflected in the flowchart of FIG. 1 b.

Software Implementations in Accordance with the First SystemArchitecture

Software implementations in accordance with the first systemarchitecture of FIG. 1 are included in the computer program listing ofthe present application, which is incorporated by reference herein. Suchsoftware implementations include the PAIR Insight™ 2009 program; thePAIR Insight™ 2010 program; and the Pair Access™ program.

A Second System Architecture

One or more preferred embodiments of the present invention are nowdescribed in connection with FIGS. 2-2 a.

FIG. 2 is a schematic illustration of another system architecture andFIG. 2a is a flowchart illustrating steps of one or more preferredembodiments in accordance with this system architecture.

In the system architecture of FIG. 2, information about patentproperties is acquired electronically from the USPTO 10 by a patentpractitioner 12 at law firm 34 using a computer, which may include adesktop pc, laptop, or server of the practitioner, and thenelectronically saved to a cloud storage location (CSL). Cloud storagelocations are readily available as a service provided by such companiesas, for example, Rackspace US, Inc. and EMC Corporation. Data may beuploaded and downloaded by any of several different protocols, as willbe understood by the Ordinary Artisan. A protocol that has been foundsuitable in terms of speed and security is the secure file transferprotocol (SFTP). Another protocol found to be suitable is the securehypertext transfer protocol (HTTPS). Furthermore, a combination ofdifferent protocols may be used including, for example, FTPS foruploading to a cloud storage location and HTTPS for downloading from acloud storage location.

In one or more preferred embodiments, the cloud storage locationutilizes an FPT server and includes first cloud storage that is indexedby customer numbers, indicated at 40 as CSL_((CNs)); and second cloudstorage that is indexed by the name associated with the PKI digitalcertificate being used, indicated at 42 as CSL_((PKI Name)). When viewedvia an FTP client program, the directory structure includes a foldertitled “cns”, in which are contained folders bearing titlescorresponding to customer numbers. Each of these folders includes datapertaining to the customer number represented by that folder. In thisway, data associated with a customer number can be accessed by simplyaccessing the data in the folder corresponding to the respectivecustomer number. Similarly, the directory structure further includes afolder titled “practitioner”, in which are contained folders bearingtitles corresponding to practitioner names associated with PKI digitalcertificates. Each of these folders includes data pertaining to thepractitioner whose PKI digital certificate is used, and data associatedwith a particular practitioner can be accessed by simply accessing thedata in the folder corresponding to that practitioner.

The PKI name preferably is the name that is literally identified whenthe PKI digital certificate is read as a text file. It is believed thatthe PKI name uniquely identifies a patent practitioner. It will beappreciated by the Ordinary Artisan that, to the extent that the PKIname is not unique, then another unique identifier should be used in itsplace that represents a single patent practitioner to which the PKIdigital certificate is issued by the USPTO. Such a unique identifiercould be issued by a third party service provider who may provide, forexample, the cloud storage location, the software for accessing thecloud location for uploading and downloading, or both.

With reference to FIG. 2a , the patent practitioner accesses, via theInternet, Private PAIR and downloads 16 from the USPTO, for eachcustomer number with which the patent practitioner is associated, theXML data for all of the patent properties associated with that customernumber. Such data conventionally may be manually downloaded bynavigating to the customer number filter in Private PAIR, selecting adesired customer number, and then selecting the orange “XML” button.However, in accordance with preferred embodiments, the downloading isprogrammatically performed on demand, automatically at a scheduled time,or automatically after a predetermined period of time has elapsed. Thedownload occurs if the XML data has not yet been downloaded for the dayand the XML data is needed. It is believed that the data that isavailable for download via Private PAIR is updated daily, and that onlyone download per day is necessary.

Optionally, detailed XML data may be separately downloaded for each ofone or more specific patent properties for purposes of supplementing theinformation about such patent property that is contained in the customernumber download. Such a download includes detailed information that isnot included in the general customer number download, such as a historyof transactions and outgoing correspondence for the specific patentproperty, and title and continuity information of the specific patentproperty. This information can be important, for example, in bettercalculating deadlines when docketing. Such detailed XML informationconventionally may be manually downloaded by navigating to theApplication Data tab for the particular patent property in Private PAIRand then selecting the orange “XML” button. However, in accordance withone or more preferred embodiments, the downloading is programmaticallyperformed when certain conditions are met that indicate such detailedinformation is needed.

Once the download of the customer number XML data is complete, the XMLdata from the downloaded files is processed 18 resulting in an initialdataset comprising a plurality of data tables. During the processing,the data from each of the downloaded XML files is reformatted andconsolidated together. The data tables include an Application Data Tablein which primary information about patent properties is stored; a Statusand Transaction Data Table in which status and transaction data isstored; and a Correspondence Data Table in which outgoing correspondenceinformation sent by the USPTO in connection with the patent propertiesis stored. The initial dataset is in the form of an in-memory dataset;however, it will be appreciated that, rather than use in-memorydatasets, one or more databases may be used. For example, objects may beused instead of data tables, and the objects may be stored, accessed,and manipulated using a database management system such as DB4O.

Also during processing, additional data may be derived from the datathat has been downloaded from the USPTO and saved, including deadlinesthat may be calculated from the downloaded data. The derived data may beincluded in one or more data tables of the initial dataset. Forinstance, reminders regarding deadlines can be derived from thedownloaded data and then saved in a reminders data table of the initialdataset.

The initial dataset is saved 54 by creating, for each customer number, acustomer number dataset representing a subset of the initial datasetthat includes all of the data associated with the patent propertiesassociated with the particular customer number. Each customer numberdataset then is saved to the cloud storage location and, in particular,to the first cloud storage CSL_((csn)) in the folder that corresponds tothe particular customer number of the customer number dataset. Anycurrently existing customer number dataset in the first cloud storagemay be overwritten during the save operation.

Provided there are no previous modifications or additions by thepractitioner that need to be accounted for (thus permitting steps 56 and58 to be skipped in FIG. 2a ), the initial dataset is used to generateand display reports to the patent practitioner; to generate and sendalerts and reports via email to the patent practitioner, or otherdesired recipients; and to instantiate a docket of the patentpractitioner. Additionally, the data may be filtered when generatingreports, alerts or instantiating a docket so that only those patentproperties of particular interest are included. Alternatively, suchfiltering may be performed when the initial dataset is created.

On the other hand, there may be modifications or additions to the dataof the initial dataset. In this respect, the practitioner may desire tomodify the data in the initial dataset after downloading—includingupdating, revising, and omitting data—or may desire to add data for usein reports, alerts, and docketing, such as data for new matters that arenot reflected in the data downloaded from the USPTO. The patentpractitioner is able to modify and add 26 data via different graphicaluser interfaces, including the ability to add matters and to addreminders for specific matters. The modifications and additions are madeto the in-memory dataset representing the initial dataset. The resultingin-memory dataset constitutes a working practitioner dataset (PracDs),and the reports, alerts, and docket are all generated based on thePracDs rather than the initial dataset.

A practitioner modifications (PM) dataset is created 28 in which the netmodifications and additions to the initial dataset are maintained. Thenet modifications and additions comprise the differences in the PracDsover the initial dataset. The PM is saved 60 to the cloud storagelocation and, in particular, to the second cloud storageCSL_((PKI Name)) in the folder that corresponds to the particularpractitioner name of the PKI digital certificate being used. Anycurrently existing PM in the second cloud storage may be overwrittenduring the save operation.

It will be appreciated that the initial dataset is thereby maintained ina pristine form based on the XML data that is acquired from the USPTO,and the initial dataset is not altered by any modifications or additionsthat are be made by the practitioner.

Furthermore, it will be appreciated that when net modifications andadditions have previously been saved to the second cloud storage, thenet modifications and changes are downloaded 56 from the second cloudstorage and applied 58 to the initial dataset that is created followingthe download of the XML data in order to create the PracDs for use inreports, alerts and docketing. Thus, steps 56 and 58 are not skipped.Instead, the PracDs is constructed each time XML data is downloaded fromthe USPTO by applying any previously saved PM to the initial dataset.

It is believed that the data that is available for download via PrivatePAIR is updated daily, and that only one download per day is necessary.Consequently, it will be appreciated that if the XML data has beendownloaded for the day, and if the PracDs needs to be constructed forreports, alerts and docketing, then the PracDs can be constructed bydownloading 62 the previously saved customer number datasets from thefirst cloud storage and combining 64 them to form the initial dataset,thereby avoiding any need to access Private PAIR and again download theXML data from the USPTO for all of the customer numbers. Accordingly, acheck may be performed before initiating XML data downloading form theUSPTO, and the download may occur if the XML data has not yet beendownloaded for the day and the XML data is needed. However, if the checkindicates that the XML data has already been downloaded for theparticular day, then no download from the USPTO is initiated, and thecustomer number datasets already created from the XML data that has beendownloaded for that particular day is read from the first cloud storagefor constructing the PracDs.

The check may include maintaining a timestamp for each XML downloadassociated with a customer number and deeming any download occurringafter a preset time as having obtained, for that day and for thatcustomer number, the most recent XML data available for that customernumber.

The ability to construct the PracDs from the customer number datasetsafter the XML data has been downloaded from the USPTO on a particularday can be particularly beneficial, as the downloading of the XML datafrom the USPTO may take an appreciable amount of time that may benoticeable to a user seeking to work with and waiting for the PracDs tobe constructed. Additionally, if Private PAIR is down or otherwiseunavailable, the PracDs still can be constructed for reports, alerts anddocketing by using the most recently saved customer number datasets andPM. This ability to read and construct the PracDs from the data saved tothe cloud storage location under such scenarios is reflected in theflowchart of FIG. 2 a.

Software Implementations in Accordance with the Second SystemArchitecture

A software implementation in accordance with the second systemarchitecture of FIG. 2 is included in the computer program listing ofthe present application, which is incorporated by reference herein. Suchsoftware implementation comprises the Searchlight program.

A Third System Architecture

One or more preferred embodiments of the present invention are nowdescribed in connection with FIGS. 3-3 a.

FIG. 3 is a schematic illustration of another system architecture andFIG. 3a is a flowchart illustrating steps of one or more preferredembodiments in accordance with this system architecture. The systemarchitecture of FIG. 3 is similar to that of FIG. 2, and only thedifferences are discussed herein, the foregoing descriptioncorresponding to FIGS. 2-2 a applying to that of FIGS. 3-3 a exceptwhere noted or where logic necessarily dictates otherwise.

In accordance with the system architecture of FIG. 3, the law firm 34includes a docket clerk 44. The docket clerk utilizes the PKI digitalcertificate of the practitioner 12 for accessing Private PAIR anddownloading the XML data for the patent properties associated with allof the customer numbers of the law firm 34 (with which the patentpractitioner's PKI digital certificate presumably is associated). TheXML data that is downloaded from each customer number is then processed18, resulting in the initial dataset. As before, the initial dataset isthen saved 54 by creating, for each customer number, a customer numberdataset representing a subset of the initial dataset that includes allof the data associated with the patent properties associated with thatparticular customer number. Each customer number dataset then is savedto the cloud storage location and, in particular, to the first cloudstorage CSL_((csn)) in the folder that corresponds to the particularcustomer number of the customer number dataset. Any currently existingcustomer number dataset in the first cloud storage may be overwrittenduring the save operation.

Provided there are no previous modifications or additions by the docketclerk that need to be accounted for (thus permitting steps 66 and 68 tobe skipped in FIG. 3a ), the initial dataset is used to generate anddisplay reports to the docket clerk; to generate and send alerts andreports via email to the docket clerk, or other desired recipients; andto instantiate a docket of law firm 34.

On the other hand, there may be modifications or additions to the dataof the initial dataset. In this respect, the docket clerk may desire tomodify the data in the initial dataset after downloading—includingupdating, revising, and omitting data—or may desire to add data for usein reports, alerts, and docketing, such as data for new matters that arenot reflected in the data downloaded from the USPTO. The docket clerk isable to modify and add 70 data via different graphical user interfaces,including the ability to add matters and to add reminders for specificmatters. The modifications and additions are made to the in-memorydataset representing the initial dataset. The resulting in-memorydataset constitutes a working docket clerk dataset (ClerkDs), and thereports, alerts, and docket are all generated based on the ClerkDsrather than the initial dataset.

For each customer number, a docket clerk modifications (DCM) dataset iscreated 72 from the ClerkDs that comprises the differences in theClerkDs over the initial dataset. The DCM for each customer number thenis saved 74 to the first cloud storage in association with that customernumber and, in particular, is saved in the folder that corresponds tothe particular customer number. Any currently existing DCM for thatcustomer number in the first cloud storage may be overwritten during thesave operation.

It will be appreciated that the initial dataset is thereby maintained ina pristine form based on the XML data that is acquired from the USPTO,and the initial dataset is not altered by any modifications or additionsthat are be made by the docket clerk.

Furthermore, it will be appreciated that when net modifications andadditions by the docket clerk have previously been saved to the firstcloud storage, the net modifications and changes are downloaded 66 fromthe first cloud storage and applied 68 to the initial dataset that iscreated in order to create the ClerkDs for use in reports, alerts anddocketing. Thus, steps 66 and 68 are not skipped when there is one ormore DCMs.

It is believed that the data that is available for download via PrivatePAIR is updated daily, and that only one download per day is necessary.Consequently, it will be appreciated that if the XML data has beendownloaded for the day, and if the ClerkDs needs to be constructed forreports, alerts and docketing, then the ClerkDs can be constructed bydownloading 62 the previously saved customer number datasets from thefirst cloud storage and combining 64 them to form the initial dataset,thereby avoiding any need to access Private PAIR and again download theXML data from the USPTO for all of the customer numbers. Accordingly, acheck may be performed before initiating XML data downloading form theUSPTO, and the download may occur if the XML data has not yet beendownloaded for the day and the XML data is needed. However, if the checkindicates that the XML data has already been downloaded for theparticular day, then no download from the USPTO is initiated, and thecustomer number datasets already created from the XML data that has beendownloaded for that particular day is read from the first cloud storagefor constructing the ClerkDs.

The check may include maintaining a timestamp for each XML downloadassociated with a customer number and deeming any download occurringafter a preset time as having obtained, for that day and for thatcustomer number, the most recent XML data available for that customernumber.

The ability to construct the ClerkDs from the customer number datasetsafter the XML data has been downloaded from the USPTO on a particularday can be particularly beneficial, as the downloading of the XML datafrom the USPTO may take an appreciable amount of time that may benoticeable to a user seeking to work with and waiting for the ClerkDs tobe constructed. Additionally, if Private PAIR is down or otherwiseunavailable, the ClerkDs still can be constructed for reports, alertsand docketing by using the most recently saved customer number datasetsand DCMs. This ability to read and construct the ClerkDs from the datasaved to the first cloud storage under such scenarios is reflected inthe flowchart of FIG. 3 a.

The practitioner 12 also has the ability to work with reports, alertsand docketing.

In this respect, and with reference now to FIG. 3b , the practitioner 62downloads the previously saved customer number datasets from the firstcloud storage and combines 64 them to form the initial dataset. Next,for each customer number, any associated DCM is downloaded 76 andapplied 78 to the initial dataset, resulting in the ClerkDs. Thepractitioner modifications (PM) dataset, if any, then is downloaded 56from the second cloud storage and applied 80 to the ClerkDs, resultingin the Practitioner Dataset (PracDs).

The practitioner, in working with reports, alerts or docketing, maydesire to modify the data in the PracDs—including updating, revising,and omitting data—or may desire to add data for use in reports, alerts,and docketing, such as data for new matters that are not reflected inthe ClerkDs. The practitioner is able to modify and add 82 data viadifferent graphical user interfaces, including the ability to addmatters and to add reminders for specific matters. The modifications andadditions are made to the in-memory dataset representing the PracDs.Thereafter, when the practitioner is finished working with the reports,alerts, or docketing, a new practitioners modifications (PM) dataset iscreated 84 from the PracDs representing the differences in the PracDsover the ClerkDs. The new PM then is saved 86 to the second cloudstorage.

It will be appreciated that the data may be filtered when generatingreports, alerts or instantiating a docket so that only those patentproperties of particular interest are included. Alternatively, suchfiltering may be performed when the ClerkDs or PracDs is created by thepractitioner.

It will further be appreciated that the initial dataset and the ClerkDsis not altered by any actions of the practitioner. Indeed, the ClerkDsis constructed from the XML data download from the USPTO and the netmodifications and additions made by the docket clerk. No action by thepractitioner affects this data. ON the other hand, the PracDs ismodified by the practitioner, whereby the practitioner may thuscustomize the data to his or her own purposes without affecting the dataused by the docket clerk as well as other in the firm. As such, thereports, alerts and docketing provided for each respective practitionerare personal to—and within the individual control of—that practitioner.

Finally, with additional reference to FIGS. 3 and 3 b, it will beappreciated that if the docket clerk does not download the XML data fora particular day before the practitioner runs his or her program, and ifPrivate PAIR is available and is not down, then the practitioner will—atleast for that day—access and download 16 the XML data from the USPTO,process the data 18, and create and save 54 the customer number datasetsto the first cloud storage location.

A Fourth System Architecture

One or more preferred embodiments of the present invention are nowdescribed in connection with FIG. 4.

FIG. 4 is a schematic illustration of another system architecture. Thesystem architecture of FIG. 4 is similar to that of FIG. 3, and only thedifferences are discussed herein, the foregoing descriptioncorresponding to FIGS. 3-3 a applying to that of FIG. 4 except wherenoted or where logic necessarily dictates otherwise.

In accordance with the system architecture of FIG. 4, a client 46 of thelaw firm 34 has access to data regarding that client's patent propertiesfor generating reports, email alerts, docketing, or combination thereof.Access by the client to the data is enabled by providing the client aprogram that is configured to download, from the second cloud storage 42and, specifically, from the folder associated with the practitionerrepresenting the client, a dataset comprising that client's data. Theclient dataset is saved with the filename of the client reference usedby the law firm, which is presumably a unique identifier of the client.The client dataset is created from the PracDs and includes anymodifications or additions made by the practitioner, as well as anymodifications or additions made upstream of the practitioner by thedocket clerk.

Moreover, the client dataset includes the latest XML data asprogrammatically downloaded from the USPTO. Indeed, in order to insurethat the data is current as of the day, the program used by thepractitioner and the program used by the docket clerk preferably run atleast once each day for at least the purpose of updating the XML datathat is downloaded from the USPTO and updating the client dataset thatis available for access by the client.

An authentication system preferably is used to authenticate the clientbefore the client dataset is downloaded. One authentication systemmaintains an association between the practitioner name, the clientreference, and a password. When the client program is run, the cliententers the practitioner name, client reference, and password. Theprogram then looks to the credentials list in the second cloud storagethat corresponds to the practitioner name, looks up the client referencein the credentials list, and compares the password associated with theclient reference in the list to the password entered by the client. Ifthe passwords match, then the client dataset corresponding to the clientreference is downloaded from the that respective practitioner folder.

The client references and password in the credentials list preferablyare maintained by the practitioner through one or more graphical userinterfaces of the program used by the practitioner.

It will be appreciated that using the program, the client is able toprogrammatically monitor information about that client's patentproperties using the most current data, all without having to manuallycontact the practitioner or law firm. Indeed, the information availableto the client is as current as the information that is available to thepractitioner. Moreover, the information is programmatically providedwithout the client having access to the practitioner's PKI digitalcertificate or associated password.

Software Implementation With Client Patent Reporting

A software implementation in which clients are provided means forgenerating reports from client datasets can be found in the computerprogram listing, which is incorporated herein by reference.Specifically, the Patent Reporter™ enables a client to enter a clientreference and associated password and, upon authentication, downloadthat client's data and view reports that are generated with the data.The credentials list that is used in with the patent reporter ismaintained by a practitioner as a feature of the Searchlight™ program,previously referenced hereinabove.

A Fifth System Architecture

One or more preferred embodiments of the present invention are nowdescribed in connection with FIG. 5.

FIG. 5 is a schematic illustration of another system architecture. Thesystem architecture of FIG. 5 is similar to that of FIG. 4, and only thedifferences are discussed herein, the foregoing descriptioncorresponding to FIG. 4 applying to that of FIG. 5 except where noted orwhere logic necessarily dictates otherwise.

In accordance with the system architecture of FIG. 5, multiplepractitioners 12,48 are explicitly shown as accessing the first cloudstorage for generating and working with reports, email and docketing.Moreover, each practitioner 12,48 saves his or her practitionermodifications (PM) dataset to the second cloud storage, as well as savesrespective client datasets and credential list to the second cloudstorage 42. Each practitioner may provide a different client access tohis or her client dataset. Thus, for example, practitioner 12 providesclient 46 with access to that client's dataset in that practitioner'sfolder in the second cloud storage 42; similarly, practitioner 48provides client 50 with access to that client's dataset in that thefolder of practitioner 48 in the second cloud storage 42. In additionthereto, each practitioner 12,48 may provide a respective client datasetgenerated from that practitioner's PracDs to the same client 52. Theclient 52 thus may generate and work with reports, email, and docketingusing either client dataset, as desired, by entering the particularpractitioner's name, the client reference (presumably the same for bothpractitioners), and the password established by the respectivepractitioner. While this may seem at first duplicitous, this dichotomycan work well when different practitioners are working on differentgroups of cases, especially for a large corporate client with manypatent properties; and when the client is a corporate client withmultiple client contacts and each desires to work with reports, email,and docketing for a selected group of patent properties of particularinterest to that client contact.

A Sixth System Architecture

One or more preferred embodiments of the present invention are nowdescribed in connection with FIG. 6.

FIG. 6 is a schematic illustration of another system architecture. Thesystem architecture of FIG. 6 is similar to that of FIG. 4, and only thedifferences are discussed herein, the foregoing descriptioncorresponding to FIG. 4 applying to that of FIG. 6 except where noted orwhere logic necessarily dictates otherwise.

In accordance with the system architecture of FIG. 6, multiple law firms34,36,38 are explicitly shown as working with a common client 46, whichis not unusual when the client is a large corporate client. The client46 has been given access by a practitioner at each law firm to thatrespective practitioner's folder in the second cloud storage 42, wherebythe client can download that client's respective dataset from each lawfirm. In the preferred embodiments in this system, the client programcombines the client datasets into a single dataset for working withreports, email and docketing. The client 46 is thereby provided acomplete and consolidated view of that client's patent properties thatare maintained by multiple law firms, with data that is the most currentavailable, even to the practitioners of the client.

ADDITIONAL IMPROVEMENTS, PROCESSES, AND OPTIMIZATIONS

In accordance with additional aspects and features the presentinvention, optimizations and processes are included in the foregoingdisclosed embodiments that are believed to minimize accessing the onlinecomputer system of the USPTO and/or facilitate efficient and synergisticcase management and docketing. Such optimizations and processes arefound in the attached source code of the computer program listing.Moreover, screenshots provided in accordance with such source code areshown in FIGS. 7-12, with an exemplary wire frame being shown in FIG.13.

Such optimizations and processes include storing data associated with adigital certificate of a practitioner at a server and first downloadingdata from the server when using the digital certificate, checking thedata for timeliness, and then proceeding to download data from the USPTOwhen the data downloaded from the server is determined to outdated;storing data associated with a particular customer number at a serverand first downloading data from the server when using a digitalcertificate associated with the particular customer number, checking thedata for timeliness, and then proceeding to download data from the USPTOwhen the data associated with the particular customer number that isdownloaded from the server is determined to be outdated. In eitherfeature, once data is downloaded from the USPTO either for a customernumber or a digital certificate, the data is uploaded to the server inassociation therewith for the benefit of others associated with thecustomer number of using the digital certificate. In addition to dataassociated with a particular customer number or a particular digitalcertificate, for data that is publicly available, such data that isdownloaded by a practitioner also may be uploaded to a server for use byothers seeking the same data. These additional optimizations andprocesses preferably are programmatically performed without action by auser.

Additional aspects comprise improvements in the user interface,including functionality and associated layout of the user controls. Forexample, with reference to FIGS. 7-12 and a corresponding wireframeshown in FIG. 13, a docketing and case management system is providedhaving an “Excel” or spreadsheet feel to it for users, wherein all ofthe data is available in grid form with direct access to the underlyingdata without searching for and modifying individual records, asexperienced current docketing systems. As another example, a tab controlis provided in which a first tab represent a listing of cases; anothertab represents a listing of events found in all of the cases, includingall status, transaction, mail, and image file wrapper events, wherebycases can be ‘looked up’ and directly viewed based on an events listing;and another tab includes deadline reminders that are programmaticallygenerated based on events.

A user interface also preferably is provided for adding, deleting, andmodifying rule sets for generating reminders, with reminders beinggenerated on user demand as well as programmatically with existingreminders being updated with revised deadlines, where appropriate andwhere such deadlines have not been marked reviewed or completed by theuser. The arrangement of information and user controls is believed to beinnovative over currently existing systems and is believed to provide asynergy and efficiently in case management and docketing that is notrealized by conventional systems. Additional tabs may be provided formanaging invention disclosures, email alerts, and subsets of the datathat are published to clients through ‘clouds’ made accessible toclients respectively.

In additional features, the case listing includes a plurality of views,including a docket inventory listing, a reverse chronologicaltransactions listing, a status listing, an examiner listing, a datadownload audit listing, a priority fields listing, an ownership listing,and a publications listing. The status, transactions, and examinerslisting preferably is grouped by status, transaction date, and examinername respectively. Moreover, as there may be a significant number ofdifferent events, each preferably is mapped to a predefined short listof transactions and status descriptions, or ignored outright if nomapping is provided, whereby an efficient and ‘noiseless’ listing ofstatus and transactions may be provided.

In accordance with one or more preferred implementations, software isprovided for automatically downloading XML data from a USPTO webplatform, processing such data to produce information regarding patentproperties, and presenting produced information to a user via a userinterface.

The present application comprises source code submitted herewith as acomputer program listing for a distributed system which includes a dataengine, an update module, and a user interface.

In accordance with one or more preferred implementations, a data engineis utilized which downloads data from a USPTO web platform. This dataengine may optionally perform some processing of this data, e g minimalprocessing.

In accordance with one or more preferred implementations, an updatemodule accesses data downloaded by the data engine, processes it toproduce information regarding patent properties, e.g. a docket, andposts it to a repository, e.g. a cloud repository.

In accordance with one or more preferred implementations, a userinterface module accesses produced information from the repository andpresents a user interface to a user which presents various views of theinformation, and optionally allows for user modification and input.

The present application discloses specific innovative aspects andfeatures in code, including specific innovative routines and subroutinesthat enable performance and enable robustness of a functioning system.The present application further discloses innovative methodologiesenabling concurrency.

Based on the foregoing description, it will be readily understood bythose persons skilled in the art that the present invention issusceptible of broad utility and application. Many embodiments andadaptations of the present invention other than those specificallydescribed herein, as well as many variations, modifications, andequivalent arrangements, will be apparent from or reasonably suggestedby the present invention and the foregoing descriptions thereof, withoutdeparting from the substance or scope of the present invention.Accordingly, while the present invention has been described herein indetail in relation to one or more preferred embodiments, it is to beunderstood that this disclosure is only illustrative and exemplary ofthe present invention and is made merely for the purpose of providing afull and enabling disclosure of the invention. The foregoing disclosureis not intended to be construed to limit the present invention orotherwise exclude any such other embodiments, adaptations, variations,modifications or equivalent arrangements, the present invention beinglimited only by the claims appended hereto and the equivalents thereof.

What is claimed is:
 1. A computer-implemented method for presenting agraphical user interface (GUI) at a personal computer providing accessto information from an instance of an in-memory docket that is generatedon demand by a user without manual data entry of bibliographical ortransactional information of patent properties, the instance of thein-memory docket comprising information regarding patent properties thatare associated with a customer number at the U.S. Patent & TrademarkOffice, the method comprising: (a) programmatically downloading, by thepersonal computer, from an online computer system of the United StatesPatent & Trademark Office, data relating to patent properties that areassociated with the customer number by (i) programmatically accessingover the Internet the online computer system of the United States Patent& Trademark Office, and (ii) programmatically downloading to thepersonal computer one or more XML files containing application data fora customer number; (b) programmatically constructing in transitorymemory of the personal computer, based on the downloaded data, thein-memory docket for the patent properties associated with the customernumber; and (c) programmatically displaying the graphical user interfaceproviding access to information from the instance of an in-memorydocket, the graphical user interface comprising (i) a matters displayarea configured to display a row for each patent property representing amatter in the in-memory docket, the in-memory docket including a matterfor each patent property associated with the customer number, wherein auser can click on a row to select it, (ii) a matter details display areaconfigured to display details for a matter selected via the mattersdisplay area, and (iii) an events display area configured to display aplurality of rows each corresponding to an event for a matter selectedvia the matter display area.
 2. The method of claim 1, wherein theevents configured to be displayed in the events display area includeevents based on transaction information for a patent property.
 3. Themethod of claim 1, wherein the events configured to be displayed in theevents display area include events based on status information for apatent property.
 4. The method of claim 1, wherein the events configuredto be displayed in the events display area include events based on mailinformation for a patent property.
 5. The method of claim 1, wherein theevents configured to be displayed in the events display area includeevents based on image file wrapper information for a patent property. 6.The method of claim 1, wherein the events display area comprises asearch box configured search for events matching a search query.
 7. Themethod of claim 1, wherein the events display area comprises a filterrow configured to filter the events displayed in the events displayarea.
 8. The method of claim 1, wherein the graphical user interfacefurther comprises a search box configured to allow a user to search formatters matching a search query.
 9. The method of claim 1, wherein thematters display area further comprises a filter row configured to filterthe matters displayed in the matters display area.
 10. The method ofclaim 1, wherein the matters display area is scrollable.
 11. The methodof claim 1, wherein the events display area is scrollable.
 12. Themethod of claim 1, wherein the matters display area is displayed on aleft side of the graphical user interface.
 13. The method of claim 1,wherein the matters display area is displayed on a left side of thegraphical user interface, and the matter details display area and theevents display area are displayed on a right side of the graphical userinterface.
 14. The method of claim 1, wherein the matters display areais displayed on a left side of the graphical user interface, the matterdetails display area and the events display area are displayed on aright side of the graphical user interface, and the matter detailsdisplay area is displayed above the events display area.